System and article of manufacture for enabling communication between nodes

ABSTRACT

Provided are a system and article of manufacture performed at a local node to communicate with a remote node. A first communication protocol is used to communicate with the remote node to establish a connection for a second communication protocol. Data structures are created to enable communication with the remote node to establish the connection with the remote node for the second communication protocol. An extension layer is invoked for the second communication protocol. The data structures are passed to the extension layer to use to communicate with the remote node using the second communication protocol.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.10/893,213, filed on Jul. 16, 2004, which patent application isincorporated herein by reference in its entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a method, system, and program forenabling communication between nodes.

2. Description of the Related Art

In storage environments, data access commands are communicated from ahost system to a storage controller, which manages access to the disks.The storage controller may be a card inside the host system or aseparate device. The Internet Small Computer Systems Interface (iSCSI)protocol is used for storage networks that utilize Ethernet connections,including Ethernet switches and routers. The term “iSCSI” as used hereinrefers to the syntax and semantic of the iSCSI protocol defined by theIETF (Internet Engineering Task Force) standards body, and any variantof that protocol. In current storage networks where iSCSI is utilized,the packet configuration comprises an Ethernet package encapsulating anInternet Protocol (IP) and Transmission Control Protocol (TCP) packagelayers, which further encapsulate an iSCSI package that includes one ormore SCSI commands. The Ethernet protocol provides for link-level errorchecking as the packets flow from point-to-point on any network segment(link) to determine whether data has been corrupted while passing on alink. In network data transmission operations, an initiator devicetransmits data or commands over the network to a target device. TheTCP/IP package includes an error detection code to perform an end-to-endchecking to determine at the opposite end whether the transmitted packethas changed during the transmission as the packet passes throughswitches and routers. A receiving device detecting an error will send anegative acknowledgment to the sending device to request retransmissionof those packets in which errors were detected.

The Remote Direct Memory Access (RMDA) protocol enables one network nodeto directly place information in another network node's memory withminimal demands on memory bus bandwidth and processor overhead. RDMAover TCP/IP (also known as iWARP) defines the interoperable protocols tosupport RDMA operations over standard TCP/IP networks. An RDMA NetworkInterface Card (RNIC) implements the RDMA protocol and performs RDMAoperations to transfer data to local and remote memories. Furtherdetails of the RDMA protocol are described in the specificationsentitled “RDMA Protocol Verbs Specification (Version 1.0)”, published bythe RDMA Consortium (April, 2003); “Direct Data Placement over ReliableTransports (Version 1.0)”, published by RDMA Consortium (October 2002);and “Marker PDU Aligned Framing for TCP Specification (Version 1.0)”,published by the RDMA Consortium (October 2002), and whichspecifications are incorporated herein by reference in their entirety.

One specification entitled “iSCSI Extensions for RDMA Specification(Version 1.0), by Michael Ko et al., released by the RDMA Consortium(July, 2003), which specification is incorporated herein in itsentirety, defines a protocol for providing the RDMA data transfercapabilities to iSCSI by layering iSCSI on top of RDMA.

Many of the features defined as part of RDMA over TCP/IP, also known asiWARP, were previously defined as operations in an InfiniBand network.The InfiniBand adaptor hardware supports RDMA operations. InfiniBandalso defines a set of protocols called Socket Direct Protocols (SDP)that allow a normal TCP/IP socket application to send a message acrossan InfiniBand network, in the same manner they would if they wereoperating on a TCP/IP network. Further details of the InfiniBand and SDPprotocols are described in the publication “InfiniBand™ Architecture,Specification Volume 1”, Release 1.1 (November, 2002, CopyrightInfiniBand™ Trade Association), which publication is incorporated hereinin its entirety.

BRIEF DESCRIPTION OF THE DRAWINGS

Referring now to the drawings in which like reference numbers representcorresponding parts throughout:

FIG. 1 illustrates an example of network nodes in which embodiments areimplemented;

FIG. 2 illustrates an example of a computing architecture in accordancewith the described embodiments;

FIG. 3 illustrates a packet format;

FIG. 4 illustrates information maintained on a mapping;

FIGS. 5 a, 5 b, 6 a, 6 b, 7 and 8 illustrate operations performed totransfer data in accordance with embodiments;

FIGS. 9, 10, 11 a, and 11 b illustrate embodiments including a gateway;and

FIGS. 12, 13, and 14 illustrate operations performed in the gateway toprocess and forward messages.

SUMMARY

Provided are a method, system, and program performed at a local node tocommunicate with a remote node. A first communication protocol is usedto communicate with the remote node to establish a connection for asecond communication protocol. Data structures are created to enablecommunication with the remote node to establish the connection with theremote node for the second communication protocol. An extension layer isinvoked for the second communication protocol. The data structures arepassed to the extension layer to use to communicate with the remote nodeusing the second communication protocol.

DETAILED DESCRIPTION

In the following description, reference is made to the accompanyingdrawings which form a part hereof and which illustrate severalembodiments of the present invention. It is understood that otherembodiments may be utilized and structural and operational changes maybe made without departing from the scope of the present invention.

FIG. 1 illustrates a network computing environment comprised of aplurality of computing nodes 2 a, 2 b . . . 2 n that communicate over anetwork 4. The network may comprise a Local Area Network (LAN), WideArea Network (WAN), Storage Area Network (SAN). Alternatively, the nodesmay communicate over a bus, such a SCSI bus, etc.

The nodes 2 a, 2 b . . . 2 n in FIG. 1 may operate as both initiatorsand targets. FIG. 2 illustrates components included in a node, such asnodes 2 a, 2 b, 2 c, to enable communication over the network 4. A node2 includes a processor 6, such as a central processing unit or complex,and an operating system 8. The node 2 further includes an application 14comprising a user application, such as a database program, serverprogram, etc. To perform an I/O operation, the application 14 would makea call to a SCSI layer 16 to generate a SCSI I/O request, which in turnwould make a call to an iSCSI layer 18. The iSCSI layer 18 initiatescommunication with a target node by performing an iSCSI login operation.To login, the iSCSI layer interfaces with a socket layer 20, such as aTCP socket layer, to establish communication with the remote target nodeand login. A socket layer 20 comprises a programming interface used tointerface between the iSCSI layer 18 and a network protocol in anadaptor 24. The adaptor 24 may comprise an RNIC adaptor or InfiniBand(IB) adaptor. The adaptor 24 includes an RDMA layer 26 and a networklayer 28, such as a TCP layer or InfiniBand layer, to package a packetin the transport layer for transmission over the network 4 or unpackagepackets received from the network 4.

In cases where the adaptor 24 comprises an InfiniBand adaptor, the node2 may include a Sockets Direct Protocol (SDP) layer 42, such that thesocket layer 20 interfaces with the SDP layer 42 and the SDP layer 42interfaces between the sockets layer 20 and the RDMA layer 26. InInfiniBand embodiments, the SDP layer 42 provides an interface betweenan application 14 making calls using the socket layer 20 and the RDMAlayer 26 in the adaptor 24, by implementing the socket layer 20 callsfrom the iSCSI layer 18 through RDMA calls to the RDMA layer 26 (eitherdirectly or via the IB adapter driver 44). In both InfiniBand and RNICembodiments, an iSER layer 22 is provided, such that after login, theiSCSI layer 18 would call an iSER layer 22 to make calls to the RNIC 24.The iSER layer 22 may call the RNIC 24 directly through function callsor through the RNIC driver 44 comprising an RDMA verb layer. Inembodiments where the adaptor 24 comprises an RNIC adaptor, the node 2may not include the SDP layer 42, whereas in InfiniBand adaptorembodiments, an SDP layer 42 is included.

The RDMA layer 26 may directly access registered memory locations in theinitiator and target nodes (locally or locally and remotely) in alogically contiguous fashion. A defined memory location, such as amemory region or memory window, is identified by a steering tag createdby the RDMA layer 26 and used to reference the registered memorylocation, such as memory regions 32. In RNIC implementations, thesteering tag is referred to as an STag and in InfiniBand embodiments,the steering tags are referred to as an R_Key for a Remote steering tagand as an L_Key for a Local steering tag (the generic term that is usedhere for both is #_Key). In certain embodiments, a memory region orsubset of a memory region referred to as a memory window may beregistered, where a separate STag/#_key would be associated with eachregistered memory location, region or window. The RDMA layer 26 uses theSTag/#_key to access the referenced memory location. In certainembodiments, the iSER layer 22 would call the adaptor 24 to register thememory regions by calling the RDMA verb layer 44. The RDMA verb layer 44(RNIC/IB adapter driver) comprises the device driver to interface theoperating system 8 with the adaptor 24. In response to the call from thefunction in the iSER layer 22 or SDP layer 42 to declare and register amemory location, e.g., memory region or window, the adapter driver 44would call the adaptor 24.

The RDMA layer 26 maintains a memory translation table 34, and whenregistering a memory region, would add an entry to the memorytranslation table 34 identifying the registered memory region and theSTag/#_key generated to reference that memory region to enable the RDMAlayer 26 to associate the STag/#_key with the memory region. The memorytranslation table 34 may be maintained within buffers in the adapter 24or within the memory 30. The Stags/#_Keys would be returned to the iSERlayer 22 functions requesting the registration to use for I/Ooperations.

After the adapter 24 generates and returns Stags/#_Keys to the iSERlayer 22, the iSER layer 22 may proceed with the I/O operation. The iSERlayer 22 wraps the packet received from the iSCSI layer 18 with headerinformation and the STag/R_Key received from the adapter 24 and pass thepacket to the adapter 24 to transfer.

To manage RDMA data transfers, the RDMA layer 26 maintains a send queue36, a receive queue 38, and a complete queue 40. The send queue 36 andreceive queue 38 comprise the work queues that the RDMA layer 26 uses tomanage RDMA data transfer requests. The complete queue 40 may comprise asharable queue containing one or more entries having completion entriesto provide a single point of completion notification for multiple workqueues. The queues 36, 38, and 40 may have many instances, perhaps foreach logical connection, and may be allocated by the adaptor 24 in thememory 30 or within buffers in the adaptor 24.

FIG. 3 illustrates the format of a transmitted package used with theembodiments. A SCSI command 50 (such as a read or write command), whichis generated by the SCSI layer 16, is encapsulated by the iSCSI layer 18within an iSCSI protocol data unit (PDU) 52, which is furtherencapsulated by the functions in the iSER layer 22 within an iSER header54. The iSCSI PDU 52 including a SCSI command 50 further includes aninitiator task tag (ITT) 56, which the iSCSI layer 18 assigns to everyissued iSCSI task, associated with an underlying SCSI command, toidentify the underlying SCSI I/O operation. The ITT 56 uniquelyidentifies the task session wide. When the target node responds to arequest from the initiator, the ITT 56 is used to relate the response tothe original request at the iSCSI layer 18. For instance, an ITT 56 inthe iSCSI's SCSI Response PDU from the target iSCSI layer 18, that issent when the target has completed the operation and returns operationalstatus, is used by the initiator iSCSI layer 18 to relate the target'sPDU with the original SCSI write command.

The iSER header 54 would include the Stag/R_Key used with the I/Ooperation and information indicating whether the remote node receivingthe advertised Stag/R_Key is to read or write to the memory region(window) referenced by the Stag/R_Key and the work queues related to therequest. The iSER header 54 and iSCSI PDU 52 are further encapsulated inone or more additional network layers 60, such as a TCP layer orInfiniBand network protocol layer. In certain embodiments, the networklayers 28 in the adapter 24 would assemble the iSER header 54 and PDU 52within the network layers 60, such as TCP, IB, etc. etc.

The iSER layer 22 further maintains an ITT to Stag/#_Key map 70 (FIG. 2)in the memory 30 that associates an ITT representing an iSCSI task withan STag/#_key used to transfer the data for that task, such as a read orwrite Stag/R_Key to cause the target node to read or write data throughthe RDMA channel. FIG. 4 illustrates the content of an entry 72 in themap 70, including a local/remote indicator 73 indicating whether themapping is for a local STag/L_Key or a remote Stag/R_Key. A localmapping entry associates an Stag/L_Key referencing a local memory windowor region with an ITT that is used to store (or retrieve) data locallyrelated to the I/O command and a remote mapping entry associates anSTag/R_key referencing a memory region or window on a remote node withan ITT from which data is to be read or transferred to the local memoryregion or window. The mapping entry 72 further includes the associatedITT 74 representing the iSCSI task, an Stag/#_Key 76 associated withthat task, and status information 78 on the task.

FIGS. 5 a, 5 b, 6 a, 6 b, 7, and 8 illustrate operations to process aSCSI write command in accordance with described embodiments. FIGS. 5 aand 5 b illustrate operations implemented by components in the initiatornode 2 to connect with a target node for using RDMA for an initiatornode 2 including either a RNIC or InfiniBand adaptor 24. With respect toFIG. 5 a, control begins at block 100 where the iSCSI layer 18interfaces to the socket layer 20 to communicate with the target nodeand “login” a new iSCSI connection and negotiate the various parameterswith a target node. Both the initiator and target node may include thearchitecture shown in FIG. 2 and include matching RNIC and/or InfiniBandadaptors. The operations performed in the initiator node then depend onwhether the initiator node 2 includes an RNIC or InfiniBand adaptor 24.As discussed, the initiator node 2 may load the layers and code neededto communicate based on the type of adaptor 24 installed in theinitiator node 24. For instance, if the node includes an InfiniBandadaptor, then the node would load the SDP layer 42, whereas if the nodeincludes only an RNIC adaptor, then the SDP layer 42 may not be loaded.If (at block 102) the iSCSI layer 18 connects via an RNIC adaptor 24,then the socket layer 20 communicates (at block 104) via the TCP 28networking function within the RNIC adaptor 24 to pass along the iSCSImessages to the target node and pass back to the iSCSI layer 18 thereceived responses via the socket layer 20. Otherwise, if (at block 102)the iSCSI layer 18 connects via an InfiniBand adaptor 24, the socketlayer 20 communicates (at block 106) via the SDP layer 42 to pass alongthe iSCSI messages to the target node and pass back to iSCSI layer 18the received responses via the socket layer 20. The SDP layer 42 creates(at block 108) data structures for an RDMA connection, such as a queuepair 26, 28, completion queue 40, etc., and then sends and receives themessages to/from the target via the InfiniBand adapter 24 and theInfiniBand network 4.

If (at block 110) the initiator node 2 is not willing to establish anRDMA session with the remote node via the Networking Layer in the RNICor InfiniBand adaptor 24, then the initiator node 2 would break thenegotiation connection and attempt (at block 112) to locate other RDMAcompatible target nodes. Otherwise, if (at block 110) an RDMA session isacceptable, then (at block 114) the SDP layer 42 (for InfiniBandadaptors 24) or the network layers 28 (for RNIC adaptors) (at block 114)returns the response from the target node, and continues to enable theiSCSI layer to use Socket APIs for triggering either the RNIC networkinglayer 28 or the SDP layer 42 to send and receive additional LoginRequest and Login Response messages with the target.

With respect to FIG. 5 b, after the login parameters are established,the initiator iSCSI layer 18 sends (at block 116) a last login requestPDU to the target node via socket calls which are either handled withthe networking layer (e.g., TCP) for an RNIC adaptor 24 or with the SDPlayer 42 for an InfiniBand adaptor. Upon receiving (at block 118) a lastlogin response PDU from the target, the iSCSI layer 18 invokes the iSERlayer 22 using iSER primitives and passes its socket information handles(which either point to the control structures of the networking layer 28for an RNIC adaptor 24 or SDP RDMA control structures for an InfiniBandadaptor). The iSER layer 22 then takes over (at block 120) socketcontrol structures and configures and modifies them for iSER/RDMAoperations. In the case of an InfiniBand adaptor 24, the iSER layer 22issues (at block 122) a special invocation to terminate the SDP sessionand permit the iSER layer 22 to then own and use the RDMA communicationchannel (queue pair, completion queue, etc.) that was used by SDP. TheiSCSI layer then communicates (at block 124) with the iSER layer viaRDMA for all future communications within the target node.

FIGS. 6 a and 6 b illustrate operations implemented by components in thetarget node, which may have the architecture of node 2 (FIG. 2) toconnect with the initiator node for using RDMA, where the target node 2includes either an RNIC or InfiniBand adaptor 24. The architecturedescribed with respect to FIG. 2 is used to describe the componentswithin both initiator and target nodes. With respect to FIG. 6 a, thetarget node iSCSI layer 20 enables (at block 150), via a Socket call, alistening port to await contact from the initiator node. The socketlayer 20 enables this contact either by using the networking layer 28(e.g., TCP) in an RNIC adaptor 24 or by using SDP 42 for an InfiniBandadaptor communicating over an InfiniBand network. Upon contact (at block152) from the initiator node iSCSI layer 18 via the same socketinterface, the target node negotiates with the initiator node to obtainagreement to proceed into an RDMA connection. If (at block 154) the RDMAconnection is not approved, then the target node breaks the negotiationconnection and continues to wait (at block 156) until another connectionis established. Otherwise, if the RDMA connection is approved, then theRNIC networking layer 28 at the target node, e.g., TCP, or the SDP layer42 returns (at block 160) to the iSCSI layer 18 via the socket APIresponses from the initiator node and continues to enable the iSCSIlayer to use socket APIs for triggering either the RNIC Networking layeror the SDP layer to receive and send additional Login Request and LoginResponse messages with the initiator. The target iSCSI layer 18 (atblock 162), upon receiving the last Login Request from the initiatorinvokes iSER layer 22 using iSER primitives and passes its socketinformation handle (which either points to the control structures of thenetworking layer 28 of the RNIC adapter or the SDP control structures)and a final Login Response message.

With respect to FIG. 6 b, after iSCSI invokes the iSER layer 22, theiSER layer 22 (at block 164) takes over the connection and establishesan iSER RDMA communication channel. For RNIC adaptors 24, the connectioninformation is that which the networking layer 28, e.g., TCP,established previously, for the InfiniBand adapter 24 the connectioninformation includes the RDMA connections and data structured createdand used by the SDP layer 42. In either case the RDMA RNIC or InfiniBandAdapter data/control structures are modified to permit the iSER/RDMAoperations. For an InfiniBand adaptor 24, the iSER layer 22 issues (atblock 166) a special invocation to terminate the SDP session and takeover RDMA communication from the SDP layer 42. Before the communicationprocess switches entirely into iSER RDMA mode (at block 168), the“Final” Login Response PDU, sent by target iSCSI to iSER, will be issuedto the initiator as the last message sent on the previous mode of theconnection (e.g. TCP/IP, or SDP/IB). The iSCSI layer then communicates(at block 170) through the iSER layer, which uses RDMA for all futureinteractions with initiator node.

FIG. 7 illustrates operations performed by the initiator node 2 upon aSCSI command completion and the receiving of a “send with invalidate”message from a target node having an RDMA adaptor that is capable ofsending a “send with invalidate message”. Upon receiving (at block 200)the “send with invalidate” message, if the adaptor 24 supports “sendwith invalidate”, then the adaptor 24 invalidates (at block 202) theSTag/R_key specified in the message, where the STag may be in the RDMAheader. If the initiator does not support “send with invalidate”, whichmay occur with an InfiniBand adaptor 24, then the message is forwardedto the iSER layer 22 to process. The initiator iSER layer 22 receives(at block 204) the response PDU and accesses the ITT 56 (FIG. 3) fromthe message to determine the STags or R Keys associated with theaccessed ITT in the ITT/STag map 70. If (at block 206) the STag/R_key ina “send with invalidate” message matches an STag/R_key in the ITT/STagmapping 70 and the initiator's adapter supports the automaticinvalidate, then the initiator iSER layer 22 invalidates (at block 208)any additional STags/#_Keys associated with the ITT in the mapping 70that were not invalidated by the adapter. If the adapter does notsupport the automatic invalidation or if the and STag/R_key in the “sendwith invalidate” does not match one STag/R_key in the mapping 70, thenthe iSER layer 22 invokes (at block 210) the adaptor directly toinvalidate the STag/R_key and any additional STags/#_Keys associatedwith the ITT in the mapping 70. The iSER layer 22 then hands (at block212) the SCSI Response PDU to the iSCSI layer 18 and clears up itsITT/Stag/#_Key mapping table 70. The iSCSI layer 18 then informs theSCSI layer 16 of the completion status of the operation.

FIG. 8 illustrates operations performed by the initiator node 2 upon aSCSI command completion and the receiving of a “send with immediatedata” message from a target node having an InfiniBand adaptor 24. Uponthe initiator adaptor 24 (InfiniBand or RNIC) receiving (at block 250)the “send with immediate data” message from the target InfiniBandadaptor or a “send” message, the message is passed to the iSER layer 22by the initiator adaptor 24 (at block 252) and the iSER layer calls theadapter 24 to invalidate the R_key in the “immediate data” portion ofthe message, if any. The iSER layer 22 would then cause the adapter 24to invalidate (at block 254) any #_Keys/STags associated with the ITT inthe mapping 70 that were not invalidated previously. The iSER layer 22delivers (at block 256) the SCSI Response PDU to the iSCSI layer 18 andclears up its ITT/Stag/#_Key mapping table 70. The iSCSI layer 18 theninforms the SCSI layer 16 the completion status of the operation.

Protocol Gateway

FIGS. 9, 10, 11 a, and 11 b illustrate how a gateway 302, 322, 352, and354 may be used to transfer messages between nodes. Each gateway 302,322, 352, and 354 may comprise a retransmitting hardware device throughwhich the target and initiator communicate messages, such as a switch,router, etc. The gateway 302, 322, 352, and 354 includes a protocolconverter 314, 334, 362, and 364 to process messages sent between theinitiator and target node that are being sent from one protocol toanother. Alternatively, the gateway 302 may be implemented in the targetnode or initiator node hardware. The gateways 302, 322, 352, and 354further include a protocol mapping 316, 336, 353, and 365 that providesa mapping between messages in a one protocol, such as InfiniBand, toanother protocol, such as iWARP.

FIG. 9 illustrates a target node 300 that implements iSCSI/iSER usingiWARP 306 and includes an RNIC 310 to transmit messages using the iWARPprotocol. The gateway 302 receives a message from the target node 300 onan iWARP network directed to an initiator node 304 implementing theiSCSI/iSER protocol using InfiniBand 308 and having an InfiniBandadaptor 312. The protocol converter 314 transforms the iWARP message toa message conforming to the InfiniBand protocol that is compatible withthe InfiniBand adaptor 312.

FIG. 10 illustrates a target node 320 that implements iSCSI/iSER usingInfiniBand 326 and includes an InfiniBand adaptor 330 to transmitmessages using the InfiniBand protocol. The gateway 322 receives amessage from the target node 320 in InfiniBand directed to an initiatornode 324 implementing the iSCSI/iSER protocol using iWARP 328 and havingan RNIC 332. The protocol converter 334 transforms the InfiniBandmessage to a message conforming to the iWARP protocol that is compatiblewith the RNIC adaptor 332 operating using the iWARP protocol.

FIG. 11 a illustrates an embodiment where gateways 352 and 354 worktogether to deliver an iSER/IB message from a target node 350 to aninitiator node 356 while converting the message for transmission on anintermediate iWARP Network. A target gateway 352 receiving theInfiniBand message from target 350 converts the message to a formatcompatible with the iWARP protocol and sends the converted message to aninitiator gateway 354 on an iWARP network. An initiator gateway 354receiving the iWARP message from the target gateway 352 converts themessage to a format compatible with the InfiniBand protocol used at theinitiator node 356 and then sends the converted message to an initiatornode 356. In this way, the gateways 352 and 354 are used to convert themessage for transmittal through an iWARP network between two nodes 350and 356 using the InfiniBand protocol, and including iSCSI/iSER usingInfiniBand 358, 366 and InfiniBand adaptors 360, 368. Further, inalternative embodiments, there may be any number of gateways between theinitiator and target node performing any number of conversions of themessage for use with the different possible communication protocols.

FIG. 11 b illustrates an embodiment where two gateways 372 and 374 worktogether to deliver an iSER/iWARP message from a target node 370 to aninitiator node 376 while converting the message for transmission on anintermediate InfiniBand network. A target gateway 372 receiving theiWARP message from the target node 370 converts the message to a formatcompatible with the InfiniBand protocol and sends the converted messageto an initiator gateway 374 on an InfiniBand network. An initiatorgateway 374 receiving the InfiniBand message from the target gateway 372converts the message to a format compatible with the iWARP protocol usedat the initiator node 376 and then sends the converted message to theinitiator 376 on the iWARP network. In this way, the gateways 372 and374 are used to convert he message for transmittal through an InfiniBandnetwork between two nodes 370 and 376 using the iWARP protocol, andincluding iSCSI/iSER using iWARP 378, 390 and iWARP adaptors 380, 392.Further, in alternative embodiments, there may be any number of gatewaysbetween the initiator and target node performing any number ofconversions of the message for use with the different possiblecommunication protocols.

FIGS. 9, 10, 11 a, and 11 b show the message flowing from a target nodeto an initiator node. However, the message flow may proceed from theinitiator to the target node, or between any two types of nodes. Forinstance, the gateways 352 and 354 can be repeated at this point forFIG. 11 a, and gateways 372 and 374 in FIG. 11 b can be repeated.

FIGS. 12, 13, and 14 illustrate operations performed by the protocolconverter 314 (FIG. 9), 334 (FIG. 10), 362 (FIG. 11 a), 364, 382 (FIG.11 b), and 386 to transform a message to a format compatible with thenode receiving the message from a format used by the node transmittingthe message implementing a protocol different from the protocol used bythe node that transmitted the message. With respect to FIG. 12, theprotocol converter 314, 334, 362, 364, 382, and 386 (Gateway) receives(at block 400) an iSCSI/iSER message from a target node (or from targetnode via another gateway node). If (at block 402) the message is from atarget node (or gateway from target) using iSER/iWARP and if (at block408) the iWARP message type maps to an equivalent InfiniBand message,then the protocol converter 314, 364 or 382 converts (at block 410) theiWARP message to the InfiniBand message equivalent and forwards theconverted InfiniBand message to the initiator node, e.g., 304 or 356,(or subsequent gateway) over an InfiniBand Network. The protocol mapping316, 336, 353, 365, 384 and 388 may provide pairs of equivalent messagesin the different formats, e.g., InfiniBand and iWARP, for the protocolconverter 314, 334, 362, 364, 382, and 386, which may maintain a mappingof iWARP to InfiniBand (and InfiniBand to iWARP) message types, suchthat the protocol mapping indicates how a message in one protocol formatmay be converted and map to the other protocol format. If (at block 408)the iWARP message type does not map to an equivalent InfiniBand messageand if (at block 412) the message is not an iWARP send with invalidatemessage having an STag, then the protocol converter 314, 364, or 382drops (at block 414) the message and throws an error because such aconversion is not handled by the protocol converter 314, 364 nor 382.

If (at block 412) the message is an iWARP “send with invalidate message”having an STag, then the protocol converter 314, 364 or 382 creates (atblock 416) an InfiniBand “send with (or without) solicited event”message. The protocol converter 314, 364 or 382 adds (at block 418) theSTag, referencing a direct reference to a memory location in the targetor initiator, from the iWARP message to the immediate data field in theInfiniBand message (alternatively, discard STag and prepare to sendwithout any immediate data). The protocol converter 314, 364 or 382transmits (at block 420) the converted message to the initiator (orsubsequent gateway) over the InfiniBand network. From block 410 or 420,control proceeds to block 422 where if there is a subsequent gateway,then such gateway will convert the iSER/IB message into iSER/iWARP byperforming the operations from block 440 in FIG. 13.

If (at block 402) the message from the target node was in the InfiniBandprotocol, then control proceeds to block 440 in FIG. 13. If (at block440) the transmission will continue over an iWARP network to a gateway,e.g., gateway 352, before going to the initiator and if (at block 442)the InfiniBand message type maps to an equivalent iWARP message in theprotocol mapping 353, then the protocol converter 362 converts (at block444) the InfiniBand message to the equivalent iWARP message and forwardsthe converted message to the next gateway 354 over iWARP. If (at block442) the InfiniBand message type does not map to an equivalent iWARPmessage in the protocol mapping 353 and if (at block 446) the message isnot an InfiniBand “send with immediate data” message, then an error isthrown (at block 448) and the message dropped.

If (at block 446) the message is an Infiniband “send with immediatedata” message, then the protocol converter 362 creates (at block 450) aniWARP send with invalidate (with solicited event) message and adds (atblock 452) the R_Key from the immediate data field in the InfiniBandmessage to the STag field in an iWARP “send with invalidate message”(alternatively, discard R_Key (immediate data) and setup send messagewithout the STag). The protocol converter 362 transmits (at block 454)the converted message to a gateway 354 over an iWARP network, such asshown in FIG. 11 a. From block 454 or 444, a subsequent gateway mayconvert the iSER/iWARP message to an iSER/InfiniBand message byperforming the operations from block 400.

If (at block 440) the InfiniBand transmission from the target node willnot continue over an iWARP network to a gateway before going to theinitiator node, (i.e., the InfiniBand message will continue throughGateway 322 or 374 on an iWARP network directly to the initiator 324 or376 as shown in FIG. 10 and FIG. 11 b, respectively), then controlproceeds to block 480 in FIG. 14. If (at block 480) the InfiniBandmessage type maps to an equivalent iWARP message, then the protocolconverter 334 or 386 converts (at block 486) the InfiniBand message tothe equivalent iWARP message and forwards to the initiator over iWARP.If (at block 480) the InfiniBand message type does not map to anequivalent iWARP message in the protocol mapping 336 or 388 and if (atblock 488) the message is not an InfiniBand “send with immediate data”message, then an error is thrown (at block 490) and the message dropped.

If (at block 488) the message is an Infiniband send with immediate datamessage, then the protocol converter 334 or 386 creates (at block 492)an iWARP send with invalidate (with solicited event) message and adds(at block 494) the R_Key from the immediate data field in the InfiniBandmessage into the STag field in an iWARP send with invalidate message(alternatively, discard R_Key (immediate data) and setup send messagewithout the STag). The protocol converter 334 or 386 transmits (at block496) the converted message to the initiator node over an iWARP network,such as shown in FIG. 10 or 11 b.

Described embodiments provide a technique for allowing a message to betransmitted between networks using different communication protocols byprocessing and, if necessary, converting the message to a formatcompatible with the communication protocol used by the receiving node.

ADDITIONAL EMBODIMENT DETAILS

The embodiments described herein may be implemented as a method,apparatus or article of manufacture using standard programming and/orengineering techniques to produce software, firmware, hardware, or anycombination thereof. The term “article of manufacture” as used hereinrefers to code or logic implemented in hardware logic (e.g., anintegrated circuit chip, Programmable Gate Array (PGA), ApplicationSpecific Integrated Circuit (ASIC), etc.) or a computer readable medium,such as magnetic storage medium (e.g., hard disk drives, floppy disks,tape, etc.), optical storage (CD-ROMs, optical disks, etc.), volatileand non-volatile memory devices (e.g., EEPROMs, ROMs, PROMs, RAMs,DRAMs, SRAMs, firmware, programmable logic, etc.). Code in the computerreadable medium is accessed and executed by a processor. The code inwhich preferred embodiments are implemented may further be accessiblethrough a transmission media or from a file server over a network. Insuch cases, the article of manufacture in which the code is implementedmay comprise a transmission media, such as a network transmission line,wireless transmission media, signals propagating through space, radiowaves, infrared signals, etc. Thus, the “article of manufacture” maycomprise the medium in which the code is embodied. Additionally, the“article of manufacture” may comprise a combination of hardware andsoftware components in which the code is embodied, processed, andexecuted. Of course, those skilled in the art will recognize that manymodifications may be made to this configuration without departing fromthe scope of the present invention, and that the article of manufacturemay comprise any information bearing medium known in the art.

The described operations may be performed by circuitry, where“circuitry” refers to either hardware or software or a combinationthereof. The circuitry for performing the operations of the describedembodiments may comprise a hardware device, such as an integratedcircuit chip, Programmable Gate Array (PGA), Application SpecificIntegrated Circuit (ASIC), etc. The circuitry may also comprise aprocessor component, such as an integrated circuit, and code in acomputer readable medium, such as memory, wherein the code is executedby the processor to perform the operations of the described embodiments.

In the described implementations, the physical layer utilized theEthernet protocol. In alternative implementations, alternative protocolsproviding link-to-link checksumming/CRCs (or other data detectingschemes) of the packet may be used instead of Ethernet, such as SerialAdvanced Technology Attachment (SATA), Infiniband, serial attached SCSIcable, etc.

In described implementations, the transport layer comprised the iSCSIprotocol. In alternative implementations other protocols known in theart for transmitting I/O commands in packets and providing end-to-endchecksumming/CRCs (or other data detecting schemes) may be used.

In the described implementations, the packaged I/O commands comprisedSCSI commands. In alternative implementations, the commands may be indifferent I/O command formats than SCSI, such as Advanced TechnologyAttachment (ATA).

In described embodiments, the iSCSI layer made calls to the iSER layerto access the RDMA data transfer capabilities. In additionalembodiments, data transfer protocol layers other than iSCSI, such as anapplication or other data transfer protocols, may call the iSER layer toaccess RDMA data transfer capabilities.

In alternative embodiments, the IP over InfiniBand protocol (withReliable Connections—RC) may be used instead of SDP to transmit packetsencoded using a protocol, such as TCP, across an InfiniBand network.Further details on the IP over InfiniBand protocol (with ReliableConnections—RC) are described in the publication “IP over InfiniBand:Connected Mode”, published by the IETF as“draft-kashyap-ipoib-connected-mode-01.txt” (September 2003), whichpublication is incorporated herein by reference in its entirety. Forinstance, the SDP layer can instead be substituted for a TCP stacklayered on top of an IPoIB (RC) implementation, and any part of thatTCP/IPoIB combination can be placed either within the node 2 software orthe adapter 24. In such embodiments, the IPoIB (RC) function may invokethe RDMA layer 26 as needed according to the IPoIB (RC) specification.

In additional embodiments, protocols other than TCP may be used totransmit the packets over an IP capable network, such as the StreamControl Transmission Protocol (SCTP), which protocol is defined in thepublication “Stream Control Transmission Protocol”, RFC 2960 (InternetSociety, 2000), which publication is incorporated herein by reference inits entirety.

FIGS. 5 a, 5 b, 6 a, 6 b, 7, and 8 describe specific operationsoccurring in a particular order. In alternative implementations, certainoperations may be performed in a different order, modified or removed.Moreover, steps may be added to the above described logic and stillconform to the described implementations. Further, operations describedherein may occur sequentially or certain operations may be processed inparallel. Yet further, operations may be performed by a singleprocessing unit or by distributed processing units.

The foregoing description of the implementations has been presented forthe purposes of illustration and description. It is not intended to beexhaustive or to limit the invention to the precise form disclosed. Manymodifications and variations are possible in light of the aboveteaching. It is intended that the scope of the invention be limited notby this detailed description, but rather by the claims appended hereto.The above specification, examples and data provide a completedescription of the manufacture and use of the composition of theinvention. Since many implementations of the invention can be madewithout departing from the spirit and scope of the invention, theinvention resides in the claims hereinafter appended.

1. An article of manufacture implemented at an initiator node tocommunicate with a target node, wherein the article of manufacturecauses operations, the operations comprising: communicating with thetarget node using a first communication protocol that uses an interfaceprotocol to communicate using a second communication protocol toestablish a connection for the second communication protocol; creating,with the interface protocol, data structures to enable communicationwith the target node to establish the connection with the target nodefor the second communication protocol; invoking an extension layer forthe second communication protocol; passing the data structures to theextension layer to use to communicate with the target node using thesecond communication protocol; receiving a message including a directreference to a memory location to invalidate from the target nodethrough an initiator adaptor, wherein the direct reference is compatiblewith the second communication protocol, and wherein the initiatoradaptor does not enable direct invalidating of the reference; invokingthe initiator adaptor to invalidate the direct reference in response todetermining that the direct reference does match one reference in a map;invalidating at least one direct reference indicated in the mapassociated with an indirect reference included in the invalidate messagein response to determining that the direct reference does match onereference in the map or that the direct reference is not provided; andissuing, by the extension layer, an invocation to terminate theinterface protocol, wherein the extension layer uses the data structurescreated by the interface protocol to communicate with the target node.2. The article of manufacture of claim 1, wherein the communicationswith the target node to establish the connection are made through asocket layer.
 3. The article of manufacture of claim 1, wherein thefirst communication protocol comprises a networking layer implemented inan remote network interface card (RNIC) adaptor used to communicate withthe target node, wherein the second communication protocol comprises theremote direct memory access (RDMA) protocol, and wherein the extensionlayer comprises an iSER layer to handle communication with the targetnode using the RDMA protocol.
 4. The article of manufacture of claim 1,wherein the first communication protocol comprises a socket layer,wherein the second communication protocol comprises the RDMA protocol,wherein the interface protocol comprises an SDP layer or TCP layeredover IPoIB (RC), wherein the extension layer comprises an iSER layer tohandle communication with the target node using the RDMA protocol, andwherein an InfiniBand adaptor is used to communicate with the targetnode.
 5. The article of manufacture of claim 1, wherein the extensionlayer is invoked upon receiving a last response to establish theconnection from the target node, wherein the invocation to terminate theinterface protocol is issued in response to invoking the extensionlayer.
 6. The article of manufacture of claim 5, wherein the invocationto terminate the interface protocol is issued in response to the sendingof the last response message to the target node using the interfaceprotocol in addition to invoking the extension layer.
 7. The article ofmanufacture of claim 1, wherein the extension layer performs theoperations of invoking the adaptor to invalidate the direct referenceand invalidating the at least one reference associated with the indirectreference in the invalidate message.
 8. The article of manufacture ofclaim 7, wherein the extension layer comprises an iSER layer, whereinthe target node includes an RNIC or InfiniBand adaptor, and wherein theinvoked initiator adaptor comprises an RNIC or InfiniBand adaptor. 9.The article of manufacture of claim 8, wherein the extension layer isinvoked in response to receiving a last login request from the initiatornode.
 10. The article of manufacture of claim 9, wherein the target nodefurther performs: sending a final login response to the initiator nodeusing the first communication protocol, wherein the data structures arepassed to the extension layer after sending the final login response.11. The article of manufacture of claim 1, wherein the indirectreference comprises an initiator task tag (ITT), and wherein the directreference comprises an STag or R_Key.
 12. A system implemented within aninitiator node to communicate with a target node, comprising: a computerreadable medium; code, including: a first communication protocol; asecond communication protocol; an extension layer for the secondcommunication protocol; interface protocol; circuitry at the initiatornode, which is in communication with the computer readable medium,enabled to: use the first communication protocol to use the interfaceprotocol to communicate with the target node using the secondcommunication protocol to establish a connection for the secondcommunication protocol; create, with the interface protocol, datastructures to enable communication with the target node to establish theconnection with the target node for the second communication protocol;invoke an extension layer for the second communication protocol; passthe data structures to the extension layer to use to communicate withthe target node using the second communication protocol; receive amessage including a direct reference to a memory location to invalidatefrom the target node through an initiator adaptor, wherein the directreference is compatible with the second communication protocol, andwherein the initiator adaptor does not enable direct invalidating of thereference; invoke the initiator adaptor to invalidate the directreference in response to determining that the direct reference doesmatch one reference in a map; invalidate at least one direct referenceindicated in the map associated with an indirect reference included inthe invalidate message in response to determining that the directreference does match one reference in the map or that the directreference is not provided; and issue, by the extension layer, aninvocation to terminate the interface protocol, wherein the extensionlayer uses the data structures created by the interface protocol tocommunicate with the target node.
 13. The system of claim 12, whereinthe communications with the target node to establish the connection aremade through a socket layer.
 14. The system of claim 12, wherein thefirst communication protocol comprises a networking layer implemented inan remote network interface card (RNIC) adaptor used to communicate withthe target node, wherein the second communication protocol comprises theremote direct memory access (RDMA) protocol, and wherein the extensionlayer comprises an iSER layer to handle communication with the targetnode using the RDMA protocol.
 15. The system of claim 12, wherein thefirst communication protocol comprises a socket layer, wherein thesecond communication protocol comprises the RDMA protocol, wherein theinterface protocol comprises an SDP layer or TCP layered over IPoIB(RC), wherein the extension layer comprises an iSER layer to handlecommunication with the target node using the RDMA protocol, and whereinan InfiniBand adaptor is used to communicate with the target node. 16.The system of claim 12, wherein the extension layer is invoked uponreceiving a last response to establish the connection from the targetnode, wherein the invocation to terminate the interface protocol isissued in response to invoking the extension layer.
 17. The system ofclaim 16, wherein the invocation to terminate the interface protocol isissued in response to the sending of the last response message to thetarget node using the interface protocol in addition to invoking theextension layer.
 18. The system of claim 12, wherein the extension layerperforms the operations of invoking the adaptor to invalidate the directreference and invalidating the at least one reference associated withthe indirect reference in the invalidate message.
 19. The system ofclaim 12, wherein the extension layer comprises an iSER layer, whereinthe target node includes an RNIC or InfiniBand adaptor, and wherein theinvoked initiator adaptor comprises an RNIC or InfiniBand adaptor. 20.The system of claim 19, wherein the extension layer is invoked inresponse to receiving a last login request from the initiator node. 21.The system of claim 20, wherein the target node further performs:sending a final login response to the initiator node using the firstcommunication protocol, wherein the data structures are passed to theextension layer after sending the final login response.
 22. The systemof claim 12, wherein the indirect reference comprises an initiator tasktag (ITT), and wherein the direct reference comprises an STag or R_Key.